Exchange 2007 Client Access install fails w/ "Object reference not set to instance of an object"
Hi, We're in the process of doing a Typical install of Exchange 2007 Ent (RTM) on 64-bit Win2003 Server. We ran 'setup /prepareAD' before the install and it ran through successfully. The Hub Transport install also completed successfully, but this error appears during the Client Access install: Object reference not set to instance of an object ------------------------------------------ Errors towards the end of ExchangeSetup.log: [1/30/2007 11:19:58 AM] [2] Process standard error: [1/30/2007 11:19:58 AM] [2] Ending processing. [1/30/2007 11:19:58 AM] [1] Executing 'install-ClientAccessIisWebServiceExtensions', handleError = False [1/30/2007 11:19:58 AM] [2] Launching sub-task '$error.Clear(); install-ClientAccessIisWebServiceExtensions'. [1/30/2007 11:19:58 AM] [2] Beginning processing. [1/30/2007 11:19:59 AM] [2] [WARNING] An unexpected error has occurred and a Watson dump is being generated: Object reference not set to an instance of an object. [1/30/2007 11:19:59 AM] [2] [ERROR] Object reference not set to an instance of an object. [1/30/2007 11:19:59 AM] [1] Exception : System.Management.Automation.CmdletInvocationException: Object reference not set to an instance of an object. ---> System.NullReferenceException: Object reference not set to an instance of an object. at Microsoft.Exchange.Management.IisTasks.IsapiExtension.IntStringToBoolean(String intString) at Microsoft.Exchange.Management.IisTasks.IsapiExtension.Parse(String extensionString) at Microsoft.Exchange.Management.IisTasks.IsapiExtensionList..ctor(String hostName) at Microsoft.Exchange.Management.IisTasks.InstallIisWebServiceExtensions.InternalProcessRecord() at Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord() at System.Management.Automation.Cmdlet.DoProcessRecord() at System.Management.Automation.CommandProcessor.ProcessRecord() --- End of inner exception stack trace --- at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate) at System.Management.Automation.Parser.PipelineNode.Execute(Array input, Pipe outputPipe, ArrayList& resultList) at System.Management.Automation.Parser.StatementListNode.Execute(Array input, Pipe outputPipe, ArrayList& resultList) [1/30/2007 11:19:59 AM] [1] [WARNING] An unexpected error has occurred and a Watson dump is being generated: Object reference not set to an instance of an object. [1/30/2007 11:19:59 AM] [1] [ERROR] Object reference not set to an instance of an object. [1/30/2007 11:19:59 AM] [1] [ERROR] Object reference not set to an instance of an object. ------------------------------------------ Errors in Event Log: Product: Exchange Event ID: 4999 Source: MSExchange Common Version: 8.0 Symbolic Name: ExchangeCrash Message: Watson report about to be sent to dw20.exe for process id: %1, with parameters: %2, %3, %4, %5, %6, %7, %8, %9, %10 ------------------------------------------ The ExchangeSetup.log does show that this server successfully recognized our DC as global catalog and dc. This Exchange server will be the 2nd Exchange 2007 server in our domain, would that matter? It will sit idle until our primary Exchange server dies, when we would manually import the replicated db. As implied, we currently have one Ex2007 server running successfully (installed from same CD). I'll be happy to supply any additional info. Any help is appreciated. Thanks.
January 31st, 2007 2:32am

dtp; Haave you found a solution for this as I am having the same problem? Thanks
Free Windows Admin Tool Kit Click here and download it now
February 16th, 2007 5:48pm

Garry,I believe our problem is due to some conflict between Exchange 2007 and Live Communication Server 2005. I got this Exchange error when installing after LCS2005 is already in place. If I install Ex2007 first, it completes successfully, but then I have issues with LCS2005. Documentation says these two can co-exist, but I couldn't figure it out. I was only able to work around the problem by separating them into different servers. I hope that helps you out.
February 16th, 2007 8:18pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics